fix(auth): create missing UserOptions for OAuth users - #1012

Problem

Users created through OAuth / Better Auth do not get a corresponding UserOptions record.
The regular ZTNet registration flow creates UserOptions together with the user, but the Better Auth user creation flow only creates the User record.
As a result, auth.me may receive:

user.options === null

and then fail on:

user.options.localControllerUrlPlaceholder = ...

with:

Cannot set properties of null (setting 'localControllerUrlPlaceholder')

This breaks the user settings/profile UI for OAuth-created users even though the OAuth session itself contains the correct user data.

Fix

This PR addresses both new and existing OAuth users:

• add a databaseHooks.user.create.after hook to create UserOptions after Better Auth creates a user;
• use upsert so the hook is idempotent;
• add a fallback in auth.me that creates missing UserOptions for users created before this fix;
• keep the default localControllerUrl behavior consistent with the regular registration flow.

Result

New OAuth users now get a valid UserOptions record during creation.
Existing OAuth users with missing UserOptions are automatically repaired on the next auth.me request.
No database migration is required because the UserOptions model and userId relation already exist.

Testing

Tested with an OAuth user created through Microsoft Entra ID.
Before the fix:

GET /api/trpc/auth.me -> 500
Cannot set properties of null (setting 'localControllerUrlPlaceholder')

After the fix:

• OAuth login succeeds;
• UserOptions is created;
• auth.me returns successfully;
• user settings correctly display name, email and role.